Hi everybody,
A problem occurs in my application, which can be described as follows:
In a formal module, saved many objects, they all have an attribute as enumratoin, just named them as: Jan, Feb, Mar, Apr, May
My aim is to make it display as follows, the first time I choose a value, eg Feb, the next time when I choose the value, I want it just display Mar, Apr, May.
Is it possible in doors V8.2?
Many thanks and looking for your help~
Best regards, Aven
Aven_HIT - Mon Dec 14 10:08:05 EST 2009 |
|
Re: A Problem In Enumration Attribute
kbmurphy - Mon Dec 14 11:50:13 EST 2009
The way you have described this, it's not possible.
|
|
Re: A Problem In Enumration Attribute
Aven_HIT - Tue Dec 15 01:33:36 EST 2009 kbmurphy - Mon Dec 14 11:50:13 EST 2009
The way you have described this, it's not possible.
Sincerely, Aven
|
|
Re: A Problem In Enumration Attribute
ePiallat - Tue Dec 15 04:06:28 EST 2009 Aven_HIT - Tue Dec 15 01:33:36 EST 2009
Just a litte disappoint, but thanks for your kindly reply.
Sincerely, Aven
It is impossible indeed to constrain displayed value of an enumeration while in-place editing.
But on the other hand, it is possible through triggers to prevent displaying the in-place box, and showing some dialog box instead. This dialog could of course display whatever you want.
I successfully set it up once for a similar case where I needed to control consistency of a set of object attributes with rules impacting each others, other objects and even history.
In your specific case however, I wouldn't recommend such a painful process for a single attribute. Did you consider some validation trigger instead (a "post" trigger that checks new value, displays a warning then prevents setting the wrong value?)
- Éric
|
|
Re: A Problem In Enumration Attribute
Aven_HIT - Tue Dec 15 09:54:54 EST 2009 ePiallat - Tue Dec 15 04:06:28 EST 2009
Hi,
It is impossible indeed to constrain displayed value of an enumeration while in-place editing.
But on the other hand, it is possible through triggers to prevent displaying the in-place box, and showing some dialog box instead. This dialog could of course display whatever you want.
I successfully set it up once for a similar case where I needed to control consistency of a set of object attributes with rules impacting each others, other objects and even history.
In your specific case however, I wouldn't recommend such a painful process for a single attribute. Did you consider some validation trigger instead (a "post" trigger that checks new value, displays a warning then prevents setting the wrong value?)
- Éric
Glad to see this post, coincidence, I want it to use this function in the similar way, up to now, I realized the trigger correctly, but have not find the way to achieve this aim.
Great thanks to you if you could post your example code or whatever.
Sincerely, Aven
|
|